After going through the trouble of getting this compile with a new example, I'm realizing this example should probably just be an extension or modification of the existing list.rs example. thoughts?

This was briefly mention on zulip and I tend to agree - HashMap doesn't seem like a natural fit for a List because the order is undefined - although stable in the current implementation. im::OrdMap would be a better fit for sure and would also help with your key requirement.

Example wise, yeah I'd say a strong no for another example just for the map. Every new example introduces maintenance burden. If there's a decent way to add it to the existing list example - that's cool. Otherwise I think just not having an example is fine too.

Agree that OrdMap is a better fit for this, otherwise this seems reasonable (outside of the fact that I want a better abstraction than ListIter for collections, but one thing at a time)

Also don't think this really needs a new example.

This makes a lot of sense @xStrom / @cmyr. Unfortunately I don't see the iter_mut method on im's OrdMap... might just be an oversight on their part?

That's interesting indeed. I asked it in im#138. Hopefully we'll know if this is something we could add.

@futurepaul going to close this for now, feel free to reopen if you pick it up again!